{"id":2554,"date":"2013-04-24T16:53:40","date_gmt":"2013-04-24T20:53:40","guid":{"rendered":"http:\/\/www.gravityhelp.com\/?p=2554"},"modified":"2018-05-23T18:02:54","modified_gmt":"2018-05-23T18:02:54","slug":"gravity-forms-v1-7-1-released","status":"publish","type":"post","link":"https:\/\/www.gravityforms.com\/gravity-forms-v1-7-1-released\/","title":{"rendered":"Gravity Forms v1.7.1 Released"},"content":{"rendered":"

Gravity Forms v1.7.1 is now available via automatic update and the downloads<\/a> page. This is a single fix release. It does not fix a bug in Gravity Forms. It implements a workaround to resolve a conflict caused by shortcomings in plugins that implement script and stylesheet minification such as W3 Total Cache, WP-Minify, etc. <\/p>\n

In order to workaround the limitations of plugins that implement minification we had to change how we output CSS. These plugins choke on CSS when it implements @import<\/a> statements which is commonly used to organize, manage and load CSS files. The end result is these plugins do not minify the Gravity Forms stylesheet and because they hijack the WordPress enqueue process the styles are never output on the page. The end result is the user thinks Gravity Forms is broken when in fact it is minification that is broken.<\/p>\n

For now we have reverted to enqueuing each of the CSS files individually rather than using @import<\/a> to load them from within the master stylesheet. We will be looking into ways to refine this going forward. <\/p>\n

<\/p>\n

What's New<\/h3>\n